Skip to content

Conversation

@shibayan
Copy link
Contributor

The value specified for openIdIssuer when using AAD was different from the value required by SWA, causing an inconsistency. This is fixed by constructing the URL based on the tenant ID.

Fixes #928

@alexsignly
Copy link

Any chance we can merge this please. :)

@chuanqisun
Copy link

Hi reviewers, @Timothyw0 and @cjk7989 , is it possible to have PR merged so we can get a working AAD local auth? Thank you for considering @shibayan's contribution!

@jonrimmer
Copy link

Just wasted half a day trying to figure out why my AAD auth wasn't working when deployed, because I'd used the issuer string necessary to make the emulator work.

Why hasn't this fix been reviewed/merged? Is the SWA CLI no longer being developed?

@Thijs199
Copy link

+1 also having this issue! Will this fix ever be deployed??

@shibayan shibayan closed this Sep 15, 2025
@shibayan shibayan deleted the fix-aad-login-redirect branch September 15, 2025 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AAD Custom Authentication emulation settings are not compatible with the CLI

5 participants